TLS curves configuration feature gate#2594
TLS curves configuration feature gate#2594richardsonnick wants to merge 6 commits intoopenshift:masterfrom
Conversation
📝 WalkthroughWalkthroughAdds a new public feature gate Changes
Estimated code review effortMedium — verify metadata and placement across manifests, docs, and the CRD removals. 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 golangci-lint (2.5.0)Error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented Comment |
|
Hello @richardsonnick! Some important instructions when contributing to openshift/api: |
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
features/features.go
Outdated
| mustRegister() | ||
|
|
||
| FeatureGateTLSCurvesConfiguration = newFeatureGate("TLSCurvesConfiguration"). | ||
| reportProblemsToJiraComponent("kube-apiserver"). |
There was a problem hiding this comment.
Why should problems be reported to this component?
There was a problem hiding this comment.
To clarify, I'm asking because I don't see any stakeholders from the team responsible for this component represented in the enhancement proposal as reviewers or having signed off on being on the hook for bugs and issues related to this feature.
There was a problem hiding this comment.
Hey @everettraven,
Sorry for the confusion, I'm working with @davidesalerno to add supporting docs for the new feature introduced here: #2583
We decided Networking was the best component.
|
@richardsonnick Looks like this may need a rebase and it looks like you are missing the generated file updates here. Running |
524928d to
b1e173a
Compare
Rebased and updated generated files. Thanks for the review |
|
Scheduling tests matching the |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: everettraven The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
As discussed with @richardsonnick I need to verify if Jira component and contact person values are the right ones. Should we also add some tests (see here)? /hold |
|
Tests are not required for new fates, only new fields. When you add the API tests will be important |
b1e173a to
e39035c
Compare
|
New changes are detected. LGTM label has been removed. |
|
Rebased + codegen |
|
@richardsonnick Apologies, another rebase needed here as there's a conflict to resolve |
e39035c to
557b626
Compare
|
@richardsonnick: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/retest |
|
rebase nuked some test. Fixing. |
|
@davidesalerno @richardsonnick Are you happy with the component this gate is assigned to? |
|
Is this actually superseded by #2583 ? I noticed it also adds the gate. |
Adds feature gate for TLS curves configuration in API config.
Enhancement PR: openshift/enhancements#1894
Implementation PR: #2583